Methods and apparatuses for requesting/providing assistance data associated with various satellite positioning systems in wireless communication networks

ABSTRACT

Methods and apparatuses are provided for use by devices within in wireless communication network to request and/or provide assistance data and/or other like data associated with various Satellite Positioning Systems (SPSs).

RELATED APPLICATIONS

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/081,985, filed Jul. 18, 2008, andtitled “Provision of Ephemeris and Almanac Data for Assisted-GNSSLocation Protocols”, and which is assigned to the assignee hereof andwhich is expressly incorporated herein by reference.

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/083,080, filed Jul. 23, 2008, andtitled “Support for Additional Navigation Satellite Systems in ExistingLocation Protocols”, and which is assigned to the assignee hereof andwhich is expressly incorporated herein by reference.

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/088,590, filed Aug. 13, 2008, andtitled “Support for Additional Navigation Satellite Systems in ExistingLocation Protocols”, and which is assigned to the assignee hereof andwhich is expressly incorporated herein by reference.

This patent application claims benefit of and priority to U.S.Provisional Patent Application 61/091,695, filed Aug. 25, 2008, andtitled “GNSS Request/Response Elements for IS-801-B”, and which isassigned to the assignee hereof and which is expressly incorporatedherein by reference.

BACKGROUND

1. Field

The subject matter disclosed herein relates to wireless communicationnetworks and devices and more particularly to methods and apparatusesfor use by devices within in wireless communication network to requestand/or provide assistance data and/or other like data associated withvarious Satellite Positioning Systems (SPSs).

2. Information

Position determination processes may be used to estimate or otherwisedetermine a location of a device associated with a wirelesscommunication network. In a particular example, a position determinationprocess may be implemented to estimate location coordinates for a mobiledevice such as a cellular telephone or other like mobile station. Thereare a variety of techniques available to support position determinationprocesses. For example, a Satellite Positioning System (SPS) such as theGlobal Positioning System (GPS) and/or other like systems may be used toestimate the location of a mobile station. In the context of a wirelesscommunication network, certain position determination processes mayrequire that information and/or processing tasks be shared and/ordistributed between multiple devices. For example, in certain instancesa mobile station may be assisted in some manner by one or more otherdevices as part of a position determination process. As a result, thereis often a need for such devices to communicate in some manner, forexample, via one or more position determination communication sessionsover a wireless link. Thus, one or more positioning protocols may bedeveloped to enable such position determination communication sessionsand as such support position determination processes.

SUMMARY

In accordance with one aspect, a method and/or apparatus may be providedfor use with a mobile station within a wireless communication network.The method and/or apparatus may identify assistance data associated witha Satellite Positioning System (SPS) that is used by the mobile stationto support a position determination process based, at least in part, onreceived SPS signals. The method and/or apparatus may transmit orinitiate transmission of signals representing at least one message overa wireless communication link to at least one network resource, whereinthe message includes at least one element identifying the assistancedata and a specific format of the assistance data if the assistance datais available in different formats. For example, a specific format of theassistance data may include a native format or a non-native format.

In accordance with another aspect, a method and/or apparatus may beprovided for use with a network resource within a wireless communicationnetwork. The method and/or apparatus may receive signals representing atleast one message as transmitted over a wireless communication link froma mobile station, wherein the message includes at least one elementidentifying assistance data associated with a SPS and identifying aspecific format of the assistance data if the assistance data isavailable in different formats. The method and/or apparatus may providethe assistance data via signals representing one or more messagestransmitted over a wireless communication link to the mobile station,wherein the assistance data may be associated with the SPS and ifidentified in the received message the assistance data may be providedin the specific format. For example, a specific format of the assistancedata may include a native format or a non-native format.

In certain example implementations, an SPS may include, for example, atleast one Global Navigation Satellite System (GNSS), such as, Galileo,GLONASS, Satellite Based Augmentation System (SBAS), Quasi-ZenithSatellite System (QZSS), modernized Global Positioning System (GPS),and/or the like. In certain example implementations, the assistance datamay include ephemeris data, almanac data, model data, timing data,health data, and/or other like data that may be associated with an SPS.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic block diagram illustrating an example wirelesscommunication network environment within which at least two devices maybe enabled to communicate with one another and initiate and/or otherwisesupport a position determination process, in accordance with animplementation.

FIG. 2 is a schematic block diagram illustrating certain examplefeatures of a device that may be enabled to initiate and/or otherwisesupport a position determination process in accordance with animplementation.

FIG. 3 is a flow-diagram illustrating an exemplary method that may beimplemented in one or more devices to initiate and/or otherwise supporta position determination process in accordance with an implementation.

FIG. 4 is a flow-diagram illustrating yet another exemplary method thatmay be implemented in one or more devices and/or location servers toinitiate and/or otherwise support a position determination process inaccordance with an implementation.

FIG. 5 is a block diagram illustratively depicting certain exemplaryinformation that may be included in messages transmitted between/amongcertain devices to initiate and/or otherwise support a positiondetermination process in accordance with an implementation.

FIG. 6 is a block diagram illustratively depicting certain exemplaryinformation that may be included in mobile station capability messagestransmitted between/among certain devices to support a positiondetermination process in accordance with an implementation.

DETAILED DESCRIPTION

Non-limiting and non-exhaustive aspects are described with reference tothe following figures, wherein like reference numerals refer to likeparts throughout the various figures unless otherwise specified.

Position determination processes may be used to estimate or otherwisedetermine a location of a device and in particular examples the locationof a mobile device such as a mobile station. There are a variety oftechniques available to support position determination processes. In thecontext of a wireless communication network, certain positiondetermination processes may require that information and/or processingtasks be distributed between and/or among multiple devices. For example,in certain instances a mobile station may be assisted in some manner byone or more other devices as part of a position determination process.As a result, there may be a need for such devices to communicate in somemanner, for example, via one or more communication sessions, e.g.,“position determination communication sessions” (e.g., which may supportassistance data delivery, position request/response sessions, and/orother like processes) over a wireless link. One or more positioningprotocols may be developed to enable such position determinationcommunication sessions for supporting various position determinationprocesses. Such positioning protocols may provide for assistance data,for example as received by one or more devices within a network from aSatellite Positioning Systems (SPS), to be requested by a mobile stationand to be provided to the mobile station. Such positioning protocols mayalso provide positioning instructions to a mobile station, e.g., qualityof service parameters such as desired location accuracy or responsetime, allowed or desired positioning systems if a mobile stationsupports more than one positioning system such as more than one SPS.

Thus, in accordance with certain aspects of the present description,method and apparatuses may be provided for use in a mobile stationwithin a wireless communication network. A mobile station may, forexample, be enabled to request assistance data associated with one ormore SPS from other resources in a wireless communication network, suchas, a base station, a location server (e.g., a Position DeterminationEntity (PDE), a Serving Mobile Location center (SMLC), a Gateway MobileLocation Center (GMLC), a Standalone SLMC (SAS), a Secure User PlaneLocation Platform (SUPL SLP)), and/or the like.

Thus, in accordance with an exemplary positioning protocol version, amobile station may be enabled to request assistance data associated withone or more SPS within at least one message (e.g., a PositionDetermination Data Message (PDDM), and/or the like) that is transmittedto at least one network resource. Conversely, for example, a basestation and/or the like may be enabled to provide assistance dataassociated with one or more SPS within at least one message that istransmitted to the mobile station. Here, for example, a message mayinclude at least one element (e.g., a request element, a responseelement, etc.) identifying in some manner assistance data that is beingrequested and/or provided, and (optionally) a specific format of theassistance data should the assistance data be available in differentformats.

In accordance with another exemplary positioning protocol version, amobile station may be enabled to request assistance data associated withone or more SPS within a Measure Position Response Message, ifassistance data provided in a corresponding Measure Position RequestMessage are not sufficient for the mobile station to perform therequested location measurements, or the provided assistance data are notin a format desired or supported by the mobile station.

For example, in certain implementations, various particular types ofPDDMs or assistance data information elements (IEs) may be defined andassociated with a various types of SPS and/or related associatedassistance data. Further, as applicable, certain particular types ofPDDM or assistance data information elements may include at least onedata field that identifies in some manner the specific format of theassistance data that is being requested or provided. For brevitypurposes within this detailed description, while the term “PDDM” is usedoften it should be recognized that any applicable message or messages(e.g., such as assistance data information element(s), and/or the like)may be employed. Thus, unless otherwise specifically recited, messagesand/or signal transmissions presented in claimed subject matter is notintended to be limited to PDDM(s) type messages/signals.

In other example implementations, one or more “generic” type(s) of PDDMor assistance data information elements or data fields within a PDDM orassistance data information element may be defined that may beselectively associated with one of a plurality of different SPS and/orassociated assistance data. For example, a single PDDM or assistancedata information element may be defined and selectively associated insome manner with either a first SPS or a second SPS, and/or a particulartype of assistance data related with either a first SPS or a second SPS.For example, such a single PDDM or assistance data information elementmay include at least a first data field that identifies in some mannerwhich SPS and/or related assistance data the PDDM or assistance datainformation element is associated with. The meaning and interpretationof data fields included in the PDDM or assistance data informationelement may, for example, be determined based at least in part on anidentified SPS. For example, a “generic” satellite health informationdata field or the like may be defined whose meaning may be determinedbased on a data field that identifies a particular SPS. For example, a“generic” data field may be used which has a different specific meaningfor each SPS, and therefore, treated accordingly (e.g., at a receiver)based on a data field which identifies the SPS. Further, as applicable,such a single PDDM or assistance data information element may includeone or more other data fields that identify in some manner a specificformat of the assistance data that is being requested or provided.

In certain example implementations, a mobile station may be enabled toindicate its support for various assistance data elements or formats toa network resource. Such process may be performed, for example, duringregistration in the network, wherein a mobile station reports itscapabilities to relevant network entities or via certain capabilityexchange messages. By knowing the supported assistance data types orformats, if certain assistance data types are possible in differentformats, allows a network resource (for example the PDE, SMLC, SLP, orthe like) to provide only those assistance data elements or formats in aPDDM, position request or assistance data delivery message that a mobilestation supports, if the mobile station does not support all specifiedor possible formats or format combinations for a particular SPS.

In certain example implementations, an SPS may include a GlobalNavigation Satellite System (GNSS), such as, Galileo, GLONASS, aSatellite Based Augmentation System (SBAS), Quasi-Zenith SatelliteSystem (QZSS), a modernized Global Positioning System (GPS), and/or thelike. SPS related assistance data may include, for example, ephemerisdata, almanac data, various model data (e.g., relating to atmosphericconditions), timing data, health data (e.g., relating to satellitehealth), and/or other like data associated with a given SPS. Examples ofother data associated with a given SPS include indications of rangingsignals supported by a particular SPS satellite, if a particular SPSsupports more than one signal, and the current SPS constellationconsists of satellites supporting a variety of signals. Such informationmay also include an indication of signal frequency, if a SPS usesdifferent frequencies for each satellite, for example a channelfrequency number in case of GLONASS. Assistance data may, in certainexample implementations, be provided in one or more native formats, anon-native format, and/or some other format, depending upon the SPS, thetype of assistance data, mobile station, base station, location server,type of PDDM, a request element, a response element, etc.

A native format, for example, may be a navigation message data formatthat may be used and defined by an individual SPS and specified in therespective Interface Control Document (ICD) or Interface Specification(IS) of this SPS.

A non-native format, for example, may be a navigation message dataformat which may be defined by an individual SPS or other source and maybe used for a SPS for which is not originally intended to be used for(for example, not defined in the ICD or IS of this SPS). Here, forexample, an ephemeris data format defined by GPS and specified in a GPSICD or IS but used for GLONASS may be considered as a non-native formatfor the GLONASS SPS.

The provision of non-native assistance data may have advantages incertain exemplary implementations to overcome the lack of certain nativenavigation data. For example, GLONASS navigation message data nativelydoes not include parameters or elements to model the ionosphericelectromagnetic wave propagation effects of the GLONASS signal. OtherSPS like GPS, for example, provide natively ionospheric model data.Therefore, if for example the GPS ionospheric model parameter areprovided to a GLONASS SPS receiver, the GLONASS receiver may make use ofthe ionospheric model parameters to adjust the GLONASS measurements forany ionospheric effects, e.g., by taking the different transmitfrequency of the GLONASS signals compared to GPS signals into account.

In certain example implementations, an element within a PDDM may includea request element and/or a response element that is compliant and/orotherwise operative with Telecommunications Industry Association (TIA)“IS-801-B” positioning protocol standard and/or an associatedThird-Generation Partnership Project 2 (3GPP2) positioning protocolstandard.

In other example implementations, assistance data elements may beincluded in a Radio Resource LCS Protocol (RRLP) Measure PositionRequest or Assistance Data delivery message that is compliant and/orotherwise operative with an associated Third-Generation PartnershipProject (3GPP) positioning protocol standard.

In other example implementations, assistance data elements may beincluded in a Radio Resource Control (RRC) Measurement Control Messageor Assistance Data Delivery message that is compliant and/or otherwiseoperative with an associated Third-Generation Partnership Project (3GPP)protocol standard.

Positioning protocols have been developed and standardized for use inCDMA2000 and High Rate Packet Data (HRPD) wireless communicationnetworks, for example. One example positioning protocol is oftenreferred to by its standardization identity as “IS-801” in the TIApublished standards (or “C.S0022” in 3GPP2 published standards).Currently, there are two versions of this example positioning protocol.The first version is the initial version IS-801 version 1 (or C.S0022-0version 3.0), which will simply be referred to herein as IS-801-1. Thesecond version is IS-801 version A (or C.S0022-A version 1.0), whichwill simply be referred to herein as IS-801-A. It is expected that someform of IS-801-B will soon be finalized and identified in some manner byTIA and/or 3GPP2 (e.g., perhaps as IS-801 version B (or C.S0022-Bversion 1.0), and/or other like identifiers).

Positioning protocols have also been developed and standardized for usein Global System for Mobile Communications (GSM) networks, GeneralPacket Radio Service (GPRS) networks, Enhanced Data Rates for GSMEvolution (EDGE) networks, or Universal Mobile Telecommunications System(UMTS) networks, for example. A positioning protocol standardized foruse in afore mentioned networks is often referred to Radio Resource LCSProtocol (RRLP) or Radio Resource Control (RRC) protocol. For theseprotocol versions, several releases exist and the current availablerelease is Release-7. It is expected that some form of Release-8 willsoon be finalized by the Third-Generation Partnership Project.

There is some support for sharing GPS related assistance data inexisting protocols, such as, IS-801-A, RRLP or RRC. Given the increasingavailability of other SPS (e.g., GNSS) it is in accordance with certainaspects of the present description, that it may be beneficial to developmore advanced/robust positioning protocol versions, such as, IS-801-B,or new Releases of RRLP and RRC, and/or other positioning protocolversions which may support a plurality of different SPS relatedassistance data.

Compared to existing GPS related assistance data in existing locationprotocols, new SPS, such as Modernized GPS or Quasi-Zenith SatelliteSystem (QZSS) or others may natively support the same or similarnavigation message data in multiple formats. For example, as specifiedin an Interface Control Document (ICD) for Modernized GPS or QZSS,Almanac data provided by Modernized GPS or QZSS may be in Navigation(NAV) Almanac format, Midi Almanac format, or Reduced Almanac format.Similar, satellite ephemeris and clock correction data may be in NAVformat, Civil Navigation (CNAV) format, or Civil Navigation-2 (CNAV-2)format. Similar, Universal Coordinated Time (UTC) model data may be inNAV format, Civil Navigation (CNAV) format, or Civil Navigation-2(CNAV-2) format. Therefore, a request for example for ephemeris, almanacor other SPS related assistance data may not be unambiguous anymore,since there are various different native formats possible in which thoseinformation can be provided to a device in a response message within acertain positioning protocol.

Moreover, in accordance with certain aspects of the present description,with the availability of new SPS, there exists a possibility to provideassistance data in non-native formats. For example, if a device supportsGPS and GLONASS, it may support assistance data formats native to GPSand GLONASS, but may also be enabled to support GPS specific formats foruse in GLONASS (i.e., non-native to GLONASS).

In one aspect of the present description, a mobile station may beenabled to indicate which particular non-native formats or formatcombinations are supported for each SPS. Since with the increasingavailability of new SPSs, many different new navigation message formatsmay be available, and therefore, many non-native combinations may bepossible as well. Since a mobile station may not be able to support allpossible combinations or formats, it is advantageous if a networkresource (e.g., PDE, SMLC, SLP, or the like) knows a priori whichformats may be supported by a mobile station for each SPS in order notto provide assistance data in a format which can not be used by themobile station.

Moreover, it is also recognized that positioning protocol versionnegotiation processes may be employed within wireless networks, asneeded, to allow various enabled devices to initiate and establish aposition determination communication session over a communicationchannel/link and through which certain such potentially varying types ofassistance data may be requested and/or provided in an efficient manner.

By way of example but not limitation, certain methods and apparatusesprovided herein may use one or more PDDMs or the like which may beprovided in one or more transport messages in a manner that not onlysupports IS-801-B, but also legacy and/or future versions. Furtherstill, certain methods and apparatuses may be enabled to supportlocation positioning processes in a variety of wireless communicationnetworks, such as, e.g., an Ultra Mobile Broadband (UMB) network, a HighRate Packet Data (HRPD) network a CDMA2000 1X network, and/or the like.

In accordance with certain aspects of the present description variousmethods and apparatuses are provided which may be implemented in a firstdevice that may be enabled to communicate with a second device tosupport a position determination process. By way of example but notlimitation, the first and/or second devices may include a mobilestation, or a specific apparatus, such as, a base station, a locationserver (e.g. a Position Determination Entity (PDE), Serving MobileLocation Center (SMLC), Gateway Mobile Location Center (GMLC),Standalone AGPS SMLC (SAS), SUPL Location Platform (SLP), etc.), and/orthe like. For example, in certain implementations a mobile station andbase station may be operatively enabled to communicate within a CDMAwireless communication network, and/or other applicable type of wirelesscommunication network.

Methods and apparatuses may be implemented in such devices to allow thedevices to utilize a position determination communication sessionassociated with a position determination process. The positiondetermination communication session may utilize a negotiated positioningprotocol version, depending on the capabilities of the devices involved.Thus, the methods and apparatuses may be implemented to allow fordifferent positioning protocol versions within a network. The methodsand apparatuses may, for example, be enabled to allow for or otherwisesupport backward and/or forward compatibility between variouspositioning protocol versions within a network.

In the following detailed description, numerous specific details are setforth to provide a thorough understanding of claimed subject matter.However, it will be understood by those skilled in the art that claimedsubject matter may be practiced without these specific details. In otherinstances, methods and apparatuses that would be known by one ofordinary skill have not been described in detail so as not to obscureclaimed subject matter.

Some portions of the detailed description which follow are presented interms of algorithms or symbolic representations of operations on binarydigital signals stored within a memory of a specific apparatus orspecial purpose computing device or platform. In the context of thisparticular specification, the term specific apparatus or the likeincludes a general purpose computer once it is programmed to performparticular functions pursuant to instructions from program software.Algorithmic descriptions or symbolic representations are examples oftechniques used by those of ordinary skill in the signal processing orrelated arts to convey the substance of their work to others skilled inthe art. An algorithm is here, and generally, is considered to be aself-consistent sequence of operations or similar signal processingleading to a desired result. In this context, operations or processinginvolve physical manipulation of physical quantities. Typically,although not necessarily, such quantities may take the form ofelectrical or magnetic signals capable of being stored, transferred,combined, compared or otherwise manipulated. It has proven convenient attimes, principally for reasons of common usage, to refer to such signalsas bits, data, values, elements, symbols, characters, terms, numbers,numerals, information, or the like. It should be understood, however,that all of these or similar terms are to be associated with appropriatephysical quantities and are merely convenient labels. Unlessspecifically stated otherwise, as apparent from the followingdiscussion, it is appreciated that throughout this specificationdiscussions utilizing terms such as “processing,” “computing,”“calculating,” “determining” or the like refer to actions or processesof a specific apparatus, such as a special purpose computer or a similarspecial purpose electronic computing device. In the context of thisspecification, therefore, a special purpose computer or a similarspecial purpose electronic computing device is capable of manipulatingor transforming signals, typically represented as physical electronic ormagnetic quantities within memories, registers, or other informationstorage devices, transmission devices, or display devices of the specialpurpose computer or similar special purpose electronic computing device.In the context of this particular patent application, the term “specificapparatus” may include a general purpose computer once it is programmedto perform particular functions pursuant to instructions from programsoftware.

Attention is now drawn to FIG. 1, which is a schematic block diagramillustrating an example wireless communication network environment 100within which devices may be enabled to communicate with one another andinitiate and/or otherwise support a position determination process.

In this particular example, wireless communication network environment100 includes representative devices such as a mobile station (MS) 102,one or more base stations (BS) 104, one or more Satellite PositioningSystem(s) (SPS) 106, a network 108, and a location server 110. MS 102may be enabled to communicate with BS 104 over one or more wirelesscommunication links. One or more of MS 102, BS 104, or location server110 may be enabled to acquire SPS signals transmitted by varioustransmitting resources of SPS 106, and/or otherwise be enabled tosupport certain position determination processes associated withinformation available via SPS 106.

Although the representative devices in FIG. 1 are illustrated as beingcoupled by either wireless communication links or wired communicationlinks it should be understood that in certain example implementations atleast some the devices may be coupled together via one or more wired,fiber, and/or wireless communication link(s).

Unless specifically stated otherwise, as used herein, the term “locationserver” is intended to represent one or more devices and/or one or morespecific apparatuses therein that is/are enabled to support, at least inpart, such position determination processes. Thus, while illustrated asa separate device in the example shown in FIG. 1 that may communicatevia network 108 and/or a BS 104 with MS 102, it should be understoodthat in other implementations a “location server” may be enabled tocommunicate directly and/or indirectly with MS 102 using one or morewired and/or one or more wireless communication links. Hence, in certainexample implementations, a location server may take the form of and/orotherwise operatively comprise one or more wireless transmitters,receivers, transceivers, one or more base stations, various wired and/orwireless network resources, one or more computing devices enabled asspecific apparatuses, and/or other like computing and/or communicationdevices. With this in mind, where example references are made to a basestation (BS) or a BS 104, it should be understood that such BS and/or BS104 may comprise a “location server” as broadly defined herein.Accordingly, the terms base station (BS) and location server are usedinterchangeably. Further still, in messages requesting and/or providingBS capabilities, etc., it should be understood that such requestedinformation and/or provided information may be associated with locationserver capabilities, etc.

MS 102 and/or BS 104 may be enabled to provide functionality, forexample, through the use of various wireless communication networks suchas a wireless wide area network (WWAN), a wireless local area network(WLAN), a wireless personal area network (WPAN), and so on. The term“network” and “system” are often used interchangeably. A WWAN may be aCode Division Multiple Access (CDMA) network, a Time Division MultipleAccess (TDMA) network, a Frequency Division Multiple Access (FDMA)network, an Orthogonal Frequency Division Multiple Access (OFDMA)network, a Single-Carrier Frequency Division Multiple Access (SC-FDMA)network, and so on. A CDMA network may implement one or more radioaccess technologies (RATs) such as CDMA2000, Wideband-CDMA (W-CDMA), andso on. CDMA2000 includes IS-95, IS-2000, and IS-856 standards. A TDMAnetwork may implement Global System for Communications (GSM), DigitalAdvanced Phone System (D-AMPS), or some other RAT. An OFDMA network mayimplement Long Term Evolution (LTE). GSM, W-CDMA and LTE are describedin documents from a consortium named “3rd Generation PartnershipProject” (3GPP). CDMA2000 is described in documents from a consortiumnamed “3rd Generation Partnership Project 2” (3GPP2). 3GPP and 3GPP2documents are publicly available. A WLAN may be an IEEE 802.11x network,and a WPAN may be a Bluetooth network, an IEEE 802.15x, or some othertype of network. The techniques may also be used for any combination ofWWAN, WLAN and/or WPAN. As mentioned earlier, the techniques may beimplemented for use with a UMB network, a HRPD network, a CDMA2000 1Xnetwork, GSM, WCDMA, LTE, and/or the like.

SPS 106 may, for example, include one or more of the Global PositioningSystem (GPS), a modernized GPS, Galileo, GLONASS, a Satellite BasedAugmentation System (SBAS) (such as a Wide Area Augmentation System(WAAS), a European Geostationary Overlay Service (EGNOS), aMulti-functional Satellite Augmentation System (MSAS), a GPS Aided GeoAugmented Navigation (GAGAN), or the like), Quasi-Zenith SatelliteSystem (QZSS), Compass/BeiDou, Indian Regional Navigational SatelliteSystem (IRNSS), NAVSTAR, and/or other like GNSS, a system that usessatellites from a combination of these systems, or any SPS developed inthe future, each referred to generally herein as a “SatellitePositioning System” (SPS).

Furthermore, the methods and apparatuses described herein may be usedwith position determination processes that utilize pseudolites or acombination of satellites and pseudolites. Pseudolites may includeground-based transmitters that broadcast a PN code or other ranging code(e.g., similar to a GPS or CDMA cellular signal) modulated on an L-band(or other frequency) carrier signal, which may be synchronized with SPStime. Each such transmitter may be assigned a unique PN code so as topermit identification by a remote receiver. Pseudolites may be used toaugment an SPS, for example, in situations where some SPS signals fromorbiting satellites might be unavailable, such as in tunnels, mines,buildings, urban canyons or other enclosed areas. Another implementationof pseudolites is known as radio-beacons. The term “satellite”, as usedherein, is intended to include pseudolites, equivalents of pseudolites,and possibly others. The term “SPS signals”, as used herein, is intendedto include SPS-like signals from pseudolites or equivalents ofpseudolites.

MS 102, in certain example implementations, may include a device such asa cellular or other wireless communication device, personalcommunication system (PCS) device, personal navigation device, a vehiclemountable navigation device, a tracking device, Personal InformationManager (PIM), Personal Digital Assistant (PDA), laptop or othersuitable device which may be capable of receiving wirelesscommunications.

The methodologies described herein may be implemented by various meansdepending upon the application. For example, these methodologies may beimplemented in hardware, firmware, software, or a combination thereof.For a hardware implementation, one or more processing units may beimplemented within one or more application specific integrated circuits(ASICs), digital signal processors (DSPs), digital signal processingdevices (DSPDs), programmable logic devices (PLDs), field programmablegate arrays (FPGAs), processors, controllers, micro-controllers,microprocessors, electronic devices, other electronic units designed toperform the functions described herein, or a combination thereof.

For a firmware and/or software implementation, certain methodologies maybe implemented with modules (e.g., procedures, functions, and so on)that perform the functions described herein. Any machine readable mediumtangibly embodying instructions may be used in implementing themethodologies described herein. For example, software codes may bestored in a memory of MS 102 and/or BS 104 and executed by a processingunit of the device. Memory may be implemented within a processing unitand/or external to the processing unit. As used herein the term “memory”refers to any type of long term, short term, volatile, nonvolatile, orother memory and is not to be limited to any particular type of memoryor number of memories, or type of media upon which memory is stored.

If implemented in software, functions that implement methodologies orportions thereof may be stored on and/or transmitted over as one or moreinstructions or code on a computer-readable medium. A computer-readablemedium may take the form of an article of manufacture. Acomputer-readable medium may include computer storage media and/orcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that may be accessed by a computer or like device. Byway of example but not limitation, a computer-readable medium maycomprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage,magnetic disk storage or other magnetic storage devices, or any othermedium that may be used to carry or store desired program code in theform of instructions or data structures and that may be accessed by acomputer.

“Instructions” as referred to herein relate to expressions whichrepresent one or more logical operations. For example, instructions maybe “machine-readable” by being interpretable by a machine for executingone or more operations on one or more data objects. However, this ismerely an example of instructions and claimed subject matter is notlimited in this respect. In another example, instructions as referred toherein may relate to encoded commands which are executable by aprocessing unit having a command set which includes the encodedcommands. Such an instruction may be encoded in the form of a machinelanguage understood by the processing unit. Again, these are merelyexamples of an instruction and claimed subject matter is not limited inthis respect.

Reference is now made to FIG. 2, which is a schematic block diagramillustrating certain example features of a specific apparatus 200enabled to initiate and/or otherwise support a position determinationprocess. Apparatus 200 may, for example, be implemented in some formwithin MS 102, BS 104, location server 110, and/or other like devices,as applicable, to perform or otherwise support at least a portion of theexample techniques described herein.

Apparatus 200 may, for example, include one or more processing units202, memory 204, a transceiver 210, and (optionally) an SPS receiver240, which may be operatively coupled with one or more connections 206(e.g., buses, lines, fibers, links, etc.). In certain exampleimplementations, apparatus 200 may take the form of a chipset, and/orthe like.

Processing unit 202 may be implemented in hardware, software, or acombination of hardware and software. Thus, for example, processing unit202 may represent one or more circuits configurable to perform at leasta portion of a data computing procedure or process related to theoperation of device 200. By way of example but not limitation,processing unit 202 may include one or more processors, controllers,microprocessors, microcontrollers, application specific integratedcircuits, digital signal processors, programmable logic devices, fieldprogrammable gate arrays, and the like, or any combination thereof.

Memory 204 may represent any data storage mechanism. Memory 204 mayinclude, for example, a primary memory and/or a secondary memory.Primary memory may include, for example, a random access memory, readonly memory, etc. While illustrated in this example as being separatefrom processing unit 202, it should be understood that all or part of aprimary memory may be provided within or otherwise co-located/coupledwith processing unit 202. Secondary memory may include, for example, thesame or similar type of memory as primary memory and/or one or more datastorage devices or systems, such as, for example, a disk drive, anoptical disc drive, a tape drive, a solid state memory drive, etc.

In certain implementations, secondary memory may be operativelyreceptive of, or otherwise configurable to couple to, computer readablemedium 220. As such, in certain example implementations, the methodsand/or apparatuses presented herein may take the form in whole or partof a computer readable medium 220 that may include computerimplementable instructions 208 stored thereon, which if executed by atleast one processing unit 202 may be operatively enabled to perform allor portions of the example operations as described herein.

As illustrated in FIG. 2, memory 204 may also include instructionsand/or data associated with one or more positioning protocol versions230, a particular SPS related PDDM 232 (e.g., or assistance data IE,etc.), a “generic” SPS related PDDM 234 (e.g., or assistance data IE,etc.), and/or SPS related assistance data 242. As illustrated, all orportions of SPS related assistance data 242 may also be provided withinor otherwise processed in some manner by SPS receiver 240. SPS receiver240 may be enabled to receive electromagnetic signals associated withone or more SPS.

Transceiver 210 may, for example, include a transmitter 212 enabled totransmit one or more electromagnetic signals over one or more wirelesscommunication links and a receiver 214 to receive one or more signalstransmitted over one or more wireless communication links. In certainimplementations, transceiver 210 may also support wired transmissionand/or reception, e.g., when implemented within BS 104 and/or other likedevices.

Attention is drawn next to FIG. 3, which is a flow-diagram illustratingan exemplary method that may be implemented in wireless communicationnetwork environment 100 to support a position determination process andmore particularly, to support devices in requesting and providing SPSrelated assistance data.

At block 302, a mobile station may identify that assistance data may bedesired to support a position determination process. For example, amobile station may determine that ephemeris and/or other data associatedwith an SPS may be missing, inaccurate, expired, etc. A mobile stationmay further identify that a particular (missing) assistance data (forexample ephemeris and clock correction data) may be supported inmultiple formats for a particular SPS. For example, GPS or QZSSephemeris may be supported in NAV, CNAV, or CNAV-2 formats, and/orAlmanac data may be supported in NAV Almanac, Reduced Almanac format orMidi Almanac format. A mobile station may determine that only one ofthese formats may be desired, or multiple formats may be desired.

At block 304, the mobile station may initiate transmission of at leastone message (e.g., a PDDM) over a wireless communication link to atleast one network resource (e.g., a base station, a location server, aPDE, etc.). The one or more messages may request all or part of thedesired assistance data as identified at block 302. The one or moremessages may also request that the desired assistance data be providedin one or more specific formats should such assistance data be availablein two or more formats.

For example, a mobile station may include a “Navigation message type”indication field in a message which indicates in which navigationmessage format the data is desired. In an exemplary implementation, suchmay be done by defining a bit map with bit positions for each navigationmessage type. For example, bit 1 in a bit map may be assigned to NAVformat, bit 2 may be assigned to CNAV format and bit 3 may be assignedto CNAV-2 format, or the like. A mobile station may set thecorresponding bit to value 1 (‘True’) to indicate this particular formatmay be desired, and may set other bits to value 0 (‘False’) to indicatethat this particular format may not desired or not needed.

At block 306, at least one network resource may receive all or part ofthe one or more messages as transmitted at block 302. Here, the one ormore received messages request that all or part of the desiredassistance data be provided, and should such assistance data beavailable in two or more formats, at least one desired format.

At block 308, at least one network resource may receive and/or otherwiseoperatively access all or part of the desired assistance data associatedwith at least one SPS.

At block 310, at least one network resource may initiate transmission ofat least one message (e.g., a PDDM) over a wireless communication linkto at least the mobile station. The one or more messages may provide allor part of the desired assistance data as identified initially at block302 by the mobile station and subsequently at block 306 by the networkresource, and/or received/accessed at block 308. Here, one or moremessages may also provide the desired assistance data in a requestedspecific format should such assistance data be available in differentformats. In certain implementations, a specific format may includeassistance data that is in a native format as may, for example, beprovided by an SPS. In certain implementations, a specific format mayinclude assistance data that is in a non-native format, e.g., in aformat that is not provided by an SPS.

By way of further example but not limitation, the example methods andapparatuses provided herein may allow for assistance data, such asephemeris and almanac data to be requested and/or provided within awireless network using a positioning protocol version supportingassisted-SPS/GNSS location processes. As mentioned, current locationprotocols, such as IS-801-A, RRLP, or RRC allow a location server tosend ephemeris and almanac data to a mobile station (such as a wirelessdevice, smart phone, or cellular phone), but only for the GPSconstellation. Other SPS/GNSS constellations are either alreadyavailable (e.g., GLONASS, SBAS (Satellite Based Augmentation Systems)),or are expected to be available in the near future (e.g., QZSS(Quasi-Zenith Satellite System)), etc. Furthermore, the GPS is expectedto be modernized and new ephemeris and almanac data formats are alsoexpected.

The methods and apparatuses provided herein may be implemented, forexample, to allow for such varying types/formats of assistance data tobe requested and/or provided over wireless network communication links.

One potential benefit may be that a negotiated positioning protocolversion may support a plurality of different devices, SPS, assistancedata, etc. Another potential benefit is that certain positioningprotocol versions may support various different types of messages (e.g.,PDDMs) and/or may support the use of generic message(s) that may beselectively enabled for use with a plurality of different types of SPS,assistance data, etc. Yet another potential benefit may be that theformat of such assistance data may be native or non-native to the SPSand as such operating efficiency may be increased in a mobile stationand/or network resource(s). For example, if a mobile station isoperatively enabled to receive native formatted assistance data from anSPS, then receiving such assistance data in a native format via awireless network may reduce the amount of processing that the mobilestation may support. In other example implementations, it may be thatadditional benefits exist by providing assistance data to the mobilestation in non-native format, for example, if a particular SPS does notsupport a certain type of model data. For example, as is the case withthe current GLONASS SPS, which does not provide model data forionospheric effects. Using GPS or Galileo, or other SPS model data forGLONASS may effectively overcome this limitation, since the GPS orGalileo ionospheric model data are “non-native” for the GLONASS SPS.Thus, certain example implementations may provide support within apositioning protocol version and/or associated position determinationprocesses for different assistance data formats.

Attention is drawn next to FIG. 4, which is a flow-diagram illustratingyet another exemplary method that may be implemented in wirelesscommunication network environment 100 to support a positiondetermination process.

At block 402, a network resource may determine that a positiondetermination process may be desired to locate a mobile station. Atblock 404, a network resource may determine which particular SPS or SPSsthe mobile station supports. This information may, for example, beprovided by the mobile station via one or more mobile station capabilityor other like messages prior to a location request, e.g., duringregistration in the network, or the like. In certain implementations,this information may be stored in subscriber databases and/or the likewithin the network.

At block 406, a network resource may determine the assistance data to beprovided to the mobile station in a location request or assistance datadelivery message. For example, in certain implementations, theassistance date may indicate visible satellites at a given time (e.g.,current time) at a coarse location estimate for the mobile station.

At block 408, a network resource may determine if such assistance datais available in one or more native formats, such as NAV, CNAV, orCNAV-2, etc., formats, and/or in one or more non-native formats. Theprocess then proceeds from block 409 to subsequent blocks, depending onavailability of various formats of assistance data.

If one or more non-native formats of the same assistance data areavailable, a network resource may determine, at block 408, which formator format choices are supported by the mobile station for thisparticular assistance data element and/or SPS. Information to make thedetermination may, for example, have been provided by the mobile stationin one or more mobile station capability messages prior to the locationrequest, such as a RRLP Position Capability Request/Response message, orthe like.

If multiple native formats of the same assistance data are available, anetwork resource may determine, at block 408, which native format choiceto provide to the mobile station. This determination may, for example,be based on information provided by the mobile station in one or moremobile station capability messages prior to the location request, suchas a RRLP Position Capability Request/Response message or the like,and/or on some pre-defined default assistance data format.

If multiple formats of the same assistance data are not available, anetwork resource may determine, at block 408, that native formattedassistance data is to be provided. In most implementations it isexpected that a mobile station will at least be receptive of applicationnative formatted assistance data for each supported SPS, for example, tosupport a non-assisted, standalone mode of operation.

At one of blocks 410, 412, or 414, the applicable formatted assistancedata is selected. At block 416, a network resource initiatestransmission of at least one message (e.g., a PDDM, a RRLP MeasurePosition Request, a RRLP Assistance Data Delivery, a RRC MeasurementControl, a RRC Assistance Data Delivery, or the like) over a wirelesscommunication link to the mobile station.

Attention is drawn next to FIG. 5, which is a block diagramillustratively depicting some of the information and/or data fields thatmay be provided in certain example message within wireless communicationnetwork environment 100. As mentioned previously, as part of positioningprotocol version a mobile station (MS), base station (BS) and/or othernetwork resource may transmit one or more PDDMs 504-1, . . . , 504-n,e.g., via one or more transport layer messages 502.

As illustrated in FIG. 5, for example, PDDM 504-1 may include at leastone response element 520 and/or at least one request element 530 inaccordance with a positioning protocol version. Some example responseand request elements are presented in subsequent sections.

In some example implementations, a PDDM may include (optional)information in one or more data fields that identifies in some mannerthe PDDM (e.g., data field 506), an SPS (e.g., data field 508), theassistance data (e.g., data field 510), and/or a format of theassistance data (e.g., data field 512). A PDDM may include assistancedata 242, and/or other information in the form of data/data signals.

By way of example but not limitation, in a positioning protocol versionsuch as IS-801-B and/or the like, request elements transmitted by a MSmay include one or more of the following: a Request Location Response, aRequest BS Capabilities, a Request Base Station Almanac, a Request GPSAcquisition Assistance, Request GPS Sensitivity Assistance, a RequestGPS Location Assistance, Request GPS Almanac, a Request GPS Ephemeris, aRequest GPS Navigation Message Bits, a Request GPS Almanac Correction, aRequest GPS Satellite Health Information, a Request Extended LocationResponse, a Request Extended BS Capabilities, a Request Enhanced BaseStation Almanac, a Request General Acquisition Assistance, a RequestExtended GPS Sensitivity Assistance, a Request GPS Almanac v1, a RequestExtended GPS Ephemeris, a Request Extended GPS Navigation Message Bits,a Request Extended GPS Almanac Correction, a Request Extended GPSSatellite Health Information, a Request GPS Coarse Location Assistance,a Request GPS Coarse Acquisition Assistance, a Request DGPS Assistance,a Request GPS Real-Time Integrity Information, a Request AdvancedLocation Response, a Request Advanced BS Capabilities, a RequestAdvanced UMB Base Station Almanac, a Request Advanced HRPD Base StationAlmanac, a Request Advanced 1X Base Station Almanac, a Request GNSSAcquisition Assistance, a Request GNSS Sensitivity Assistance, a RequestModernized GPS Ephemeris and Clock Correction, a Request QZSS Ephemerisand Clock Correction, a Request GLONASS Ephemeris and Clock Correction,a Request Galileo Ephemeris and Clock Correction, a Request GEONavigation Message Parameters, a Request Modernized GPS Almanac, aRequest QZSS Almanac, a Request GLONASS Almanac, a Request GalileoAlmanac, a Request GEO Almanacs Message Parameters, a Request GPSIonospheric Model, a Request GALILEO Ionospheric Model, a Request QZSSIonospheric Model, a Request GNSS-GNSS Time Offset, a Request GPS UTCModel, a Request Advanced GNSS Satellite Health Information, and/or aRequest DGNSS Assistance.

Also by way of example but not limitation, as part of IS-801-B, responseelements transmitted by a MS may include one or more of the following: aReject, a Provide Location Response, Provide MS Information, a ProvideAutonomous Measurement Weighting Factors, a Provide PseudorangeMeasurement, a Provide Pilot Phase Measurement, a Provide Time OffsetMeasurement, a Provide Cancellation Acknowledgement, am Extended Reject,a Provide Extended Location Response, a Provide Extended MS Information;a Provide Autonomous Measurement Weighting Factors v1, a Provide GeneralLocation Measurement, a Provide Extended Cancellation Acknowledgement, aProvide GPS Coarse Location Response, a Provide Messaging DelayMeasurement, a Provide Bearing Measurement, a Provide Serving SystemInformation, an Advanced Reject, a Provide Advanced Location Response, aProvide Advanced MS Information, a Provide UMB Pilot Time OffsetMeasurement, a Provide HRPD Pilot Phase Measurement, a Provide GNSSPseudorange Measurement, a Provide Advanced CancellationAcknowledgement, and/or a Provide Advanced System ParametersInformation.

By way of further example but not limitation, as part of IS-801-Brequest elements received by a MS may include one or more of thefollowing: a Request Location Response, a Request MS Information, aRequest Autonomous Measurement Weighting Factors, a Request PseudorangeMeasurement, a Request Pilot Phase Measurement, a Request Time OffsetMeasurement, a Request Cancellation, a Request Extended LocationResponse, a Request Extended MS Information, a Request AutonomousMeasurement Weighting Factors v1, a Request General LocationMeasurement, a Request Extended Cancellation, a Request GPS CoarseLocation Response, a Request Messaging Delay Measurement, a RequestBearing Measurement, a Request Serving System Information, a RequestAdvanced Location Response, a Request Advanced MS Information, a RequestUMB Pilot Time Offset Measurement, a Request HRPD Pilot PhaseMeasurement, a Request GNSS Pseudorange Measurement, a Request AdvancedCancellation, and/or a Request Advanced System Parameters Information.

By way of further example but not limitation, as part of IS-801-Bresponse elements received by a MS may include one or more of thefollowing: a Reject, a Provide Location Response, a Provide BSCapabilities, a Provide Base Station Almanac, a Provide GPS AcquisitionAssistance, a Provide GPS Sensitivity Assistance, a Provide GPS LocationAssistance—Spherical Coordinates, a Provide GPS LocationAssistance—Cartesian Coordinates, a Provide GPS Almanac, a Provide GPSEphemeris, a Provide GPS Navigation Message Bits, a Provide GPS AlmanacCorrection, a Provide GPS Satellite Health Information, an ExtendedReject, a Provide Extended Location Response, a Provide Extended BSCapabilities, a Provide Enhanced Base Station Almanac, a Provide GeneralAcquisition Assistance, a Provide Extended GPS Sensitivity Assistance, aProvide GPS Almanac v1, a Provide Extended GPS Ephemeris, a ProvideExtended GPS Navigation Message Bits, a Provide Extended GPS AlmanacCorrection, a Provide Extended GPS Satellite Health Information, aProvide GPS Coarse Location Assistance, a Provide GPS Coarse AcquisitionAssistance, a Provide DGPS Assistance, a Provide GPS Real-Time IntegrityInformation, an Advanced Reject, a Provide Advanced Location Response, aProvide Advanced BS Capabilities, a Provide Advanced UMB Base StationAlmanac, a Provide Advanced HRPD Base Station Almanac, a ProvideAdvanced 1X Base Station Almanac, a Provide GNSS Acquisition Assistance,a Provide GNSS Sensitivity Assistance, a Provide Modernized GPSEphemeris and Clock Correction, a Provide QZSS Ephemeris and ClockCorrection, a Provide GLONASS Ephemeris and Clock Correction, a ProvideGalileo Ephemeris and Clock Correction, a Provide GEO Navigation MessageParameters, a Provide Modernized GPS Almanac, a Provide QZSS Almanac, aProvide GLONASS Almanac, a Provide Galileo Almanac, a Provide GEOAlmanacs Message Parameters, a Provide GPS Ionospheric Model, a ProvideGALILEO Ionospheric Model, a Provide QZSS Ionospheric Model, a ProvideGNSS-GNSS Time Offset, a Provide GPS UTC Model, a Provide Advanced GNSSSatellite Health Information, and/or a Provide DGNSS Assistance.

Thus, as illustrated by the above example a variety of request andresponse elements may be supported within the PDDMs defined by apositioning protocol version.

Attention is drawn next to FIG. 6, which is a block diagramillustratively depicting some of the information and/or data fields thatmay be provided in certain example mobile station capability messageswithin wireless communication network 100.

As mentioned previously, many new data formats may be defined oravailable for new SPSs, and therefore, multiple native or non-nativeformatted combinations of assistance data may be possible. However, amobile station may not be able to support all possible combinations. Inorder to avoid sending assistance data information in formats notsupported by a mobile station, new enhanced mobile station capabilitiesmay be provided which may, for example, include specific informationabout supported assistance data choices for each supported SPS.

As illustrated in FIG. 6, for example, a mobile station capabilityelement 602 may include information about each supported SPS, identifiedby a particular SPS ID 604-1. For each supported SPS ID, information ofwhich specific assistance data element is supported may be provided by asupported assistance data element 606-1. If an assistance data elementmay have multiple format choices, a format choice indicator 609-1 mayincluded. As shown in this example implementation, a bit map of N FormatIDs is defined where one bit per model or format may be used to indicatesupport or non-support for a particular assistance data format orchoice. This could be done by defining a one value as support, and azero value of non-support, for example. Here, for example, for eachsupported SPS, an element 604-1, 604-2, . . . , 604-n may be included inthe mobile station capability message. For each SPS 604-n, oneassistance data element 606-1, 606-2, . . . , 606-n may be included,each indicating support for a particular assistance data type.

While there has been illustrated and described what are presentlyconsidered to be example features, it will be understood by thoseskilled in the art that various other modifications may be made, andequivalents may be substituted, without departing from claimed subjectmatter. Additionally, many modifications may be made to adapt aparticular situation to the teachings of claimed subject matter withoutdeparting from the central concept described herein.

Therefore, it may be intended that claimed subject matter not be limitedto the particular examples disclosed, but that such claimed subjectmatter may also include all aspects falling within the scope of appendedclaims, and equivalents thereof.

What is claimed is:
 1. A method in a mobile station, the methodcomprising: identifying requested assistance data associated with aSatellite Positioning System (SPS) used by said mobile station, whereinthe requested assistance data support a position determination processat the mobile station based, at least in part, on received SPS signals;and transmitting electromagnetic signals representing at least onemessage over a wireless communication link to at least one networkresource, said at least one message comprising at least one elementidentifying said requested assistance data and a specific format of saidrequested assistance data, wherein said requested assistance data isavailable in a plurality of formats.
 2. The method as recited in claim1, wherein said at least one message is associated with only said SPS.3. The method as recited in claim 2, wherein said at least one messagecomprises a data field that identifies said specific format.
 4. Themethod as recited in claim 1, wherein said at least one messagecomprises a single message that is selectively associated with one of aplurality of SPS using a first data field that identifies said SPS. 5.The method as recited in claim 4, wherein said single message comprisesa second data field identifying said specific format.
 6. The method asrecited in claim 1, wherein said SPS comprises at least one GlobalNavigation Satellite System (GNSS).
 7. The method as recited in claim 6,wherein said at least one GNSS comprises at least one of Galileo,GLONASS, Satellite Based Augmentation System (SBAS), Quasi-ZenithSatellite System (QZSS), or modernized Global Positioning System (GPS).8. The method as recited in claim 1, wherein the requested assistancedata comprises at least one of ephemeris data, almanac data, model data,timing data, or health data.
 9. The method as recited in claim 1,wherein said specific format of said requested assistance data comprisesa native format or a non-native format.
 10. The method as recited inclaim 1, wherein said at least one element comprises at least one of arequest element or a response element, and wherein said at least oneelement is compliant with at least one of a Telecommunications IndustryAssociation (TIA) IS-801-B standard or an associated Third-GenerationPartnership Project 2 (3GPP2) standard.
 11. An apparatus within a mobilestation, the apparatus comprising: means for identifying requestedassistance data associated with a Satellite Positioning System (SPS)used by said mobile station, wherein the requested assistance datasupport a position determination process at the mobile station based, atleast in part, on received SPS signals; and means for transmittingelectromagnetic signals representing at least one message over awireless communication link to at least one network resource, said atleast one message comprising at least one element identifying saidrequested assistance data and a specific format of said requestedassistance data, wherein said requested assistance data is available ina plurality of formats.
 12. The apparatus as recited in claim 11,wherein said at least one message is associated with only said SPS. 13.The apparatus as recited in claim 12, wherein said at least one messagecomprises a data field that identifies said specific format.
 14. Theapparatus as recited in claim 11, wherein said at least one messagecomprises a single message that is selectively associated with one of aplurality of SPS using a first data field that identifies said SPS. 15.The apparatus as recited in claim 14, wherein said single messagecomprises a second data field identifying said specific format.
 16. Theapparatus as recited in claim 11, wherein said SPS comprises at leastone Global Navigation Satellite System (GNSS).
 17. The apparatus asrecited in claim 16, wherein said at least one GNSS comprises at leastone of Galileo, GLONASS, Satellite Based Augmentation System (SBAS),Quasi-Zenith Satellite System (QZSS), or modernized Global PositioningSystem (GPS).
 18. The apparatus as recited in claim 11, wherein therequested assistance data comprises at least one of ephemeris data,almanac data, model data, timing data, or health data.
 19. The apparatusas recited in claim 11, wherein said specific format of said requestedassistance data comprises a native format or a non-native format. 20.The apparatus as recited in claim 11, wherein said at least one elementcomprises at least one of a request element or a response element, andwherein said at least one element is compliant with at least one of aTelecommunications Industry Association (TIA) IS-801-B standard or anassociated Third-Generation Partnership Project 2 (3GPP2) standard. 21.A mobile station comprising: at least one receiver operatively enabledto receive electromagnetic signals associated with a SatellitePositioning System (SPS); at least one wireless transceiver; and atleast one processing unit operatively coupled to said receiver and saidwireless transceiver and being operatively enabled to: identifyrequested assistance data associated with said SPS used by said mobilestation, wherein the requested assistance data support a positiondetermination process based, at least in part, on said receivedelectromagnetic signals associated with said SPS; and initiatetransmission of electromagnetic signals representing at least onemessage over a wireless communication link to at least one networkresource using said wireless transceiver, said at least one messagecomprising at least one element identifying said requested assistancedata and a specific format of said requested assistance data, whereinsaid requested assistance data is available in a plurality of formats.22. The mobile station as recited in claim 21, wherein said at least onemessage is associated with only said SPS.
 23. The mobile station asrecited in claim 22, wherein said at least one message comprises a datafield that identifies said specific format.
 24. The mobile station asrecited in claim 21, wherein said at least one message comprises asingle message that is selectively associated with one of a plurality ofSPS using a first data field that identifies said SPS.
 25. The mobilestation as recited in claim 24, wherein said single message comprises asecond data field identifying said specific format.
 26. The mobilestation as recited in claim 21, wherein said SPS comprises at least oneGlobal Navigation Satellite System (GNSS).
 27. The mobile station asrecited in claim 26, wherein said at least one GNSS comprises at leastone of Galileo, GLONASS, Satellite Based Augmentation System (SBAS),Quasi-Zenith Satellite System (QZSS), or modernized Global PositioningSystem (GPS).
 28. The mobile station as recited in claim 21, wherein therequested assistance data comprises at least one of ephemeris data,almanac data, model data, timing data, or health data.
 29. The mobilestation as recited in claim 21, wherein said specific format of saidrequested assistance data comprises a native format or a non-nativeformat.
 30. The mobile station as recited in claim 21, wherein said atleast one element comprises at least one of a request element or aresponse element, and wherein said at least one element is compliantwith at least one of a Telecommunications Industry Association (TIA)IS-801-B standard or an associated Third-Generation Partnership Project2 (3GPP2) standard.
 31. An article comprising: a non-transitory computerreadable medium having computer implementable instructions storedthereon which if implemented by one or more processing units in a mobilestation operatively enable the mobile station to: as part of a positiondetermination process, identify requested assistance data associatedwith a Satellite Positioning System (SPS) used by said mobile station,wherein the requested assistance data support a position determinationprocess at the mobile station based, at least in part, on received SPSsignals; and initiate transmission of electromagnetic signalsrepresenting at least one message over a wireless communication link toat least one network resource, said at least one message comprising atleast one element identifying said requested assistance data and aspecific format of said requested assistance data, wherein saidrequested assistance data is available in a plurality of formats. 32.The article as recited in claim 31, wherein said at least one message isassociated with only said SPS.
 33. The article as recited in claim 32,wherein said at least one message comprises a data field that identifiessaid specific format.
 34. The article as recited in claim 31, whereinsaid at least one message comprises a single message that is selectivelyassociated with one of a plurality of SPS using a first data field thatidentifies said SPS.
 35. The article as recited in claim 34, whereinsaid single message comprises a second data field identifying saidspecific format.
 36. The article as recited in claim 31, wherein saidSPS comprises at least one Global Navigation Satellite System (GNSS).37. The article as recited in claim 36, wherein said at least one GNSScomprises at least one of Galileo, GLONASS, Satellite Based AugmentationSystem (SBAS), Quasi-Zenith Satellite System (QZSS), or modernizedGlobal Positioning System (GPS).
 38. The article as recited in claim 31,wherein the requested assistance data comprises at least one ofephemeris data, almanac data, model data, timing data, or health data.39. The article as recited in claim 31, wherein said specific format ofsaid requested assistance data comprises a native format or a non-nativeformat.
 40. The article as recited in claim 31, wherein said at leastone element comprises at least one of a request element or a responseelement, and wherein said at least one element is compliant with atleast one of a Telecommunications Industry Association (TIA) IS-801-Bstandard or an associated Third-Generation Partnership Project 2 (3GPP2)standard.